Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

chore(deps): update dependency proxyquire to v2 #35

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Mar 2, 2018

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
proxyquire 1.8.0 -> 2.1.3 age adoption passing confidence

Release Notes

thlorenz/proxyquire (proxyquire)

v2.1.3

Compare Source

v2.1.2

Compare Source

v2.1.1

Compare Source

v2.1.0

Compare Source

v2.0.2

Compare Source

v2.0.1

Compare Source

v2.0.0

Compare Source

Fixes a bug where relative paths were not properly resolved and could conflict (#​190). This may break your tests if they relied on buggy behavior.


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@coveralls
Copy link

coveralls commented Mar 2, 2018

Coverage Status

Coverage remained the same at 100.0% when pulling 60ddb2b on renovate/proxyquire-2.x into 58cbea2 on master.

@renovate renovate bot force-pushed the renovate/proxyquire-2.x branch 3 times, most recently from 575b6dd to 60ddb2b Compare March 7, 2018 20:03
@renovate renovate bot force-pushed the renovate/proxyquire-2.x branch 2 times, most recently from 7cfdabc to a9980be Compare March 23, 2018 03:41
@renovate renovate bot force-pushed the renovate/proxyquire-2.x branch 2 times, most recently from 7dd47ef to 0ae53f4 Compare April 18, 2018 19:33
@renovate renovate bot changed the title chore(deps): update dependency proxyquire to v2 Update dependency proxyquire to v2 May 9, 2018
@renovate renovate bot changed the title Update dependency proxyquire to v2 chore(deps): update dependency proxyquire to v2 May 9, 2018
@renovate renovate bot force-pushed the renovate/proxyquire-2.x branch from 0ae53f4 to 76fa658 Compare May 19, 2018 01:33
@renovate renovate bot force-pushed the renovate/proxyquire-2.x branch 2 times, most recently from 923bc6a to 93f8c75 Compare August 21, 2018 18:31
@renovate renovate bot force-pushed the renovate/proxyquire-2.x branch from 3ed95f0 to 42dab73 Compare July 13, 2019 10:57
@renovate renovate bot force-pushed the renovate/proxyquire-2.x branch 2 times, most recently from 22bab93 to 6749858 Compare August 12, 2019 13:56
@commit-lint
Copy link

commit-lint bot commented Nov 21, 2019

Chore

  • deps: update dependency proxyquire to v2 (d156706)

Contributors

renovate[bot]

Commit-Lint commands

You can trigger Commit-Lint actions by commenting on this PR:

  • @Commit-Lint merge patch will merge dependabot PR on "patch" versions (X.X.Y - Y change)
  • @Commit-Lint merge minor will merge dependabot PR on "minor" versions (X.Y.Y - Y change)
  • @Commit-Lint merge major will merge dependabot PR on "major" versions (Y.Y.Y - Y change)
  • @Commit-Lint merge disable will desactivate merge dependabot PR
  • @Commit-Lint review will approve dependabot PR
  • @Commit-Lint stop review will stop approve dependabot PR

@renovate renovate bot force-pushed the renovate/proxyquire-2.x branch from 6749858 to d603d02 Compare March 3, 2021 02:32
@renovate
Copy link
Author

renovate bot commented Nov 20, 2022

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: yarn.lock
No /opt/buildpack/tools/node/7.10.1/bin/npx defined - aborting

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant